About Templates and Roles

You can use templates to reduce the amount of time that it takes to enter customer data. Common settings, such as the Class of Service and Device Type, can be saved in a template and applied to multiple users. This speeds the configuration process and ensures that correct settings are applied throughout the enterprise.

NOTE: As of MiVoice Business Release 7.2, MiVoice Business nodes can SDS share data with a MiCollab server 7.0 or up, in support of the Flow Through Provisioning solution, which allows the administrator to configure and manage users and phone services from a single location - MiCollab is the recommended option. See Adding Users and Services for more information.

When MiVoice Business is sharing data with a MiCollab server, templates that include MiCollab services are displayed in the User and Service Templates form, but they cannot be used (copied) to create a new template or deleted from ESM. These templates can be managed only through the MiCollab USP application, which you can access automatically by clicking the "Open in MiCollab" link. However, you can modify parts of the template that are controlled by ESM, such as, phone or user details.

 

Template Forms

Three templates forms are available:

Default Templates

The system has two default templates which can be used in place of customized templates:

You can update the default templates, but you cannot rename or delete them. The default User and Service Template consists of one user and one service with Voicemail. You cannot add or delete the user or phone service, but you can delete the Voicemail option.

Managing Templates

You can add, change and delete the Key and User Roles templates. You can modify and delete the User and Service Templates. To create a new User and Service Template, you must copy an existing template and save it with a new name. You can also import data from a . CSV file into templates.

NOTES

 

Sharing Templates

Templates and roles are shared. In a network of mixed releases, MiVoice Business (MiVB) Release 7.0 templates are shared only with MiVB 7.0 and up systems. However, Pre-7.0 (MCD 5.x and 6.x) templates are shared with and visible on all nodes (5.x, 6.x, 7.x and up). Once shared, a pre-7.0 template can be modified on a 7.x system (within its limitations, such as, one phone service per user) and still remain compatible with pre-7.0 systems. When a pre-7.0 template is copied on a 7.x system, the new copy becomes a 7.x template and is no longer shared with pre-7.0 systems.

User Roles associated with the Default or a pre-Release 7.0 template are shared with all nodes (MiVB Release 7.x, 6.x, and 5.x). Roles associated with 7.0 templates are NOT shared with the older systems, which do not support 7.0 templates.

MiVB 7.x User and Service Template can only use 7.x Key Template; however, the Default Key Template can be used for both 7.x User and Service Templates and pre-7.0 User and Device Templates.

When MiVoice Business is sharing data with a MiCollab server, templates that include MiCollab services are displayed in the User and Service Templates form, but they cannot be used (copied) to create a new template and they cannot be deleted from the ESM.

Example

To use templates to program users in your enterprise, follow these steps:

  1. Add a Key template for each device type.

  2. Create a User and Service Template for each department or work group (e.g. Marketing, Finance). To integrate a Key template with the User and Service Template, select the appropriate device type (Key template).

  3. Create User Roles, selecting the appropriate User and Service Template for each role.

  4. Add users, selecting the appropriate User Role with the associated template for each entry.

NOTE: Data in key templates associated with a User Role are not imported. If you are importing users and specify a User Role in the spreadsheet, the role will survive the import but not the programming in the role's key template. Key programming will either need to be manually added in the Multiline Set Keys form after the user is imported or imported via the Key Assignment worksheet in the Import Spreadsheet.